Write metrics files in various formats. 🔼

Requested by Evilham -

I'd be mpre interested jn generating a prometheus metrics file

A thing I also like is to have a list of IPs and hostnames and the chain pf how they got pulled in the mix

Text file, it should be easy to add

I haven't gotten around to doing that on my thing

[url=https://prometheus.io/docs/concepts/data_model/#notation]https://prometheus.io/docs/concepts/data_model/#notation[/url]

I'd have to check the current output :-) just thought I'd mention what I consider worthy of having

The chain on which hostnames and ips are pulled is useful to know where things are going wrong

And the prometheus metrics (sth like debmirrorsarecords, debmirrorsfauptya_records)

The metrics are useful because we can track that info over time

And know if things are regularly bad or something


reported=2019-06-25 08:17:41

reporter=onefang

priority=normal

category=Feature

severity=feature

resolution=fixed


2019-09-10 04:37:32 onefang: For myself I would also add RRD (I use Collectd and CGraphz) and likely

an interface for Icinga/Nagios.


2019-11-05 08:35:20 onefang: "a list of IPs and hostnames and the chain pf how they got pulled in the mix" is now done, it's apt-panopticon-report-DNS.lua

apt-panopticon-report-DNS.lua has now been folded into apt-panopticon-report-email-web.lua.


2019-12-10 06:54:15 onefang: RRD has been added, and a modified CGP, which was the inspiration for CGraphz, though CGraphz is too clunky for just showing graphs to the public.


2019-12-25 13:18:06 onefang: Icinga/Nagios -

For a particular host, check results/host.lua, count errors, warnings, and maybe timeouts.


2019-12-25 14:38:33 onefang: Everything except the prometheus metrics file, since I have asked Evilham a few times for exactly what he wants and examples, with no response.  We have RRD anyway, that should be enough.  If he supplies more details later, I'll reopen this.